|
2020-09-15 12:37 developer |
|
|
|
Hi Jason, I think you don't have full log for this issue. As you mentioned, QA remove RCU battery and install again, But I don't find any disconnect event in attached log files. Please try again and describe detailed reproduce procedure. Thanks ! |
|
|
HI Kerwin this morning , we explained it to you. if you give a solution, please leave it here. Thanks. |
|
|
Hi Jason, I did a test and found it isn't related to Brightness setting. As I show to you, issue happens as long as you keep pressing "Enter" key. From BT Snoop file, I see a disconnect event due to timeout. The behavior is the same as Android 9, I suggest to put this as low priority since Android 9 is already on the market for 1 year. Thanks ! |
|
|
hi kerwin per talking , it is related to matis 841 side effect issue. please fix for mantis 841 and this ticket soon. Thanks |
|
|
Fixed in v15.522.3 (20200924) |
|
|
hi kerwin before confirmed it, please didn't close it. if you need to close it, please inform to us. if you fix this issue, you need to explain it about your modifications. Thanks. |
|
|
hi kerwin we tested with v15.522.4a. when press a long key, it don't proceed a key about 12 times ( volume up / down) and it is working again after a while. please let me know why does happen not working duration. |
|
|
Hi Jason, We need log to find the reason, please attach log when you report issue. Thanks ! |
|
|
hi kerwin you can reproduce it in your side. of cause, we also upload it when procedure it again. but you have to reproduce this issue in your side. |
|
|
Hi Jason, I think what you say is about the time to send "key up" event while you long press on a RCU key. Right now, the timer is set to 1.5 seconds in kernel driver. (Mantis 0000841 https://mantis.cnsbg.foxconn.com/vaas/view.php?id=841) If you want to choose another value, please let us know. Thanks! |
|
|
HI Kerwin. as you know it, we didn't apply 841 solution in android p. so smart3 box didn't see same problem. you said to me android q don't need to make work around solution in android q. why do you need to apply a solution of mantis 841 in android q ? Let me know a reason. as the time is shorter more, what is increasing? if set 1 sec, what happen ? |
|
|
Hi Jason, Please check Mantis#0000841 again. We add the fix in Android 10. The time define when driver send "key up" event. We can change the time if there is no application level concerns. But I don't think it is necessary to change current value. |
|
|
hi kerwin. if you don't have any side effect, we need to reduce some gap. since we also need to help user don't feel RCU not working. please reduce as 1 sec. if you don't have some concern point, please let me know it. Thanks. |
|
|
Hi Jason, If the timer is reduced to 1 sec, UI will stop changing more earlier. Is the result as what you expect ? We can also disable "auto key-up" timer only for "enter" key. Then, user can change brightness value by keep pressing "enter" key. Please let us know which one you want to do for this issue. 1. keep "auto key-up" timer for "enter" key, with 1 sec duration 2. disable "auto key-up" timer for "enter" key |
|
|
hi kerwin I don't catch UI will stop changing more earlier. please explain it more. 1. please give test FW as interval 1s. 2. if disable "auto key-up", it happen same issue as mantis 841. is it right? |
|
|
hi kerwin. as compare with SWAN box, skb manager ask to me onething. when press a button during 3s more, it made an event 1 times as long key. long key는 press 상태에서 3초이상 누르고 있으면 1회 발생하도록 되어있습니다. is this symptom related to the timer is set to 1.5 seconds in kernel driver ? you comment at 4531 " you say is about the time to send "key up" event while you long press on a RCU key." |
|
|
Hi Jason, Please see Jim's commit about "center" key. We disable "auto-up" key in both Smart3 and SWAN project. They are using the same driver and the driver doesn't handle long press key event, Thanks ! center_key.png (9,771 bytes) |
|
|
hi kerwin you mean it is equal to below comment on mantis 1044. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1044 my rcu question don't care of below item. please confirm it. I will implement as we discussed in Wechat: 1.press < 3 seconds then release => short signal 2.press >= 3 seconds then release => long signal |
|
|
Hi Jason, What you mentioned is for "Front Panel" key, not BT RCU key. (Mantis 1044) The implementation are different. Please double check about your question. |
|
|
Hi kerwin sorry ..it is my question is wrong, I ask to you again. 1. On Eagle project , also apply it as like mantis 1044 ? or don't need to apply it for Eagle project( smart3,UHD4 in android p and BTF in android 10) ? , if didn't apply it,, we need to apply it. 2. why does you make as disable for Auto key up ? who does request this factor to you? if disable for auto key up, There is no problem for mantis 841 issue ? |
|
|
1. On Eagle project , also apply it as like mantis 1044 ? or don't need to apply it for Eagle project( smart3,UHD4 in android p and BTF in android 10) ? , if didn't apply it,, we need to apply it. ==> It is for SWAN front panel keys. We don't need in on Smart3/UHD4. 2. why does you make as disable for Auto key up ? who does request this factor to you? if disable for auto key up, There is no problem for mantis 841 issue ? ==> It is a mistake to include "center" key for "auto-up". Unlike CH+/CH- and other keys, "center" is sent only once from RCU. |
|
|
hi kerwin. for smart3/ uhd4 , also used for finding RCU KEY and for entering recovery mode for upgrading via USB . So if it is a bad solution for this project, skb manager also want to apply it . if don't accept it , please let me know a reason. |
|
|
Hi Jason, I don't understand your request. The purposes and drivers of front panel key are different on Smart3 and SWAN. |
|
|
hi kerwin if don't want to accept my requirement, please check one item on Eagle box. when push front key during 3s more, does we send a long signal or not ? only for finding RCU and entering recovery mode, Does we send a combination key ? |
|
|
Hi Jason, For finding RCU, we send 'SKB_FUNC_18' key event after long pressing front panel key. This is handled in AML kernel driver. For entering recovery mode, we don't send send key event since it is handled directly in AML bootloader. These implementations are done on Smart3 for more than 1 year. |
|
|
hi kerwin it is closed. |
- yk.jung ( (ALTech) Younkwang Jung ) developer
